Import Blocks

Importing mining blocks instead of generating them

Import Mining Blocks

To access this dialog:

The Import Mining Block Solids task is used to import previously-generated mining blocks into your Studio OP project.

This task is only available if the Import the mining blocks from an existing file option was selected during the Select Workflow Method task.

To import blocks and submit them for evaluation, sequencing and scheduling, you will need to map specific attributes in the incoming file to expected data entities in Studio OP. For example, you can determine which, if any, elements of your file represent the phase excavation order, block identification values, phase naming and/or pre-established sequencing.

If no fields are mapped, the specified file will be treated as a single phase representing a single block, without sequencing information. By nominating fields in the input file, you can refine your evaluation results and introduce more granular block data into downstream functions as part of operational scheduling.

Field Details:

The Import Mining Block Solids panel is used primarily to determine the attributes of your incoming file and what they represent.

Pit: select the pit to which the imported blocks belong. Pits are set up using the Manage task.

Delete Existing Solids: imported blocks will be added to any previously-imported blocks (allowing block data to be accumulated within your project over time). You can clear out any previously-imported blocks with this command.

Mining Blocks: locate the Datamine file containing your block data. As a minimum, a Block ID attribute must exist. The remaining fields are options but can be a field representing the chronological phase order and phase name to which each block belongs, a bench attribute and potentially a sequence attribute if the data has already been sequenced.

You can choose any loaded wireframe object, or use the browse button to choose any wireframe triangle file.

Other non-system attributes can also be imported - see Attributes to import, below.

BLOCKID: the attribute that identifies blocks within your wireframe file. This is a mandatory selection. If an attribute called "BLOCKID" exists within the imported/selected file, it will be automatically chosen. Otherwise, any non-system numeric field can be picked.

Phase order: this attribute represents the numeric field governing the order in which your phases will be mined. You don't have to specify a Phase order field, but if you don't all blocks within the file will be treated as if they are within a single phase.

Phase name: only available if a phase order has been selected, this is the attribute (alphanumeric or numeric) that describes each phase. If no name is specified, a default naming convention will be used in Studio OP to name each phase, using the format:

P#Pit number#_PH#Phase Number#

e.g. "P1_PH2"

If a Phase name is specified, the attribute value will be used instead of the default naming convention.

Bench Name: if bench information is encoded within the imported blocks file, specify the bench attribute here. If no Bench name attribute is specified, the imported data will be treated as a single bench.

Sequence: if block data has been sequenced, specify the Sequence attribute here. You can either accept the embedded information or generate new sequence data using the Reserves ribbon's Sequence task.

Attribute to import: all attributes that are not reserved for system use, and have not been specified above, are available for import using this table. Choose any attribute(s) that you wish to bring into Studio OP alongside your block data (e.g. Strata information or a model sequence number, or colour, for example) by selecting the respective check box(es).

Import Block Solids: once you've set everything up, click Import Block Solids to import your data and inject it into your project's database.

Display Options: once mining block solids have been added to the project you can display them as blocks and/or outlines using the following options:

  • Show mining block solids for the pit

  • Show mining block outlines for the pit

  openbook.gif (910 bytes)   Related Topics

 

Select Workflow MethodMining Block Evaluation
Operational Scheduling
Define a SequenceThe Reserves Workflow